Skip to content

ENT-14398: Moved event driven cfengine into cf-reactor - #6290

Open
victormlg wants to merge 1 commit into
cfengine:masterfrom
victormlg:agent-driven-cf-reactor
Open

ENT-14398: Moved event driven cfengine into cf-reactor#6290
victormlg wants to merge 1 commit into
cfengine:masterfrom
victormlg:agent-driven-cf-reactor

Conversation

@victormlg

Copy link
Copy Markdown
Contributor

No description provided.

@victormlg
victormlg force-pushed the agent-driven-cf-reactor branch from a26acb5 to 22ff75c Compare August 14, 2026 11:17
Comment thread cf-reactor/cf-reactor.c Fixed
@victormlg
victormlg marked this pull request as ready for review August 18, 2026 08:09
@victormlg
victormlg force-pushed the agent-driven-cf-reactor branch 2 times, most recently from 4407d5a to be99f9c Compare August 20, 2026 08:45
@victormlg
victormlg requested a review from larsewi August 20, 2026 09:45

@larsewi larsewi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that cf-watchd has some options not present here. Is this intended?

Comment thread cf-reactor/cf-reactor.c Outdated
Comment thread cf-reactor/cf-reactor.c Outdated
Comment thread cf-reactor/cf-reactor.c Fixed
@victormlg
victormlg force-pushed the agent-driven-cf-reactor branch 2 times, most recently from 78cb159 to 1468b22 Compare August 21, 2026 08:14
@victormlg
victormlg requested a review from larsewi August 21, 2026 09:24
@victormlg

Copy link
Copy Markdown
Contributor Author

@cf-bottom jenkins, please :)

@cf-bottom

Copy link
Copy Markdown

@victormlg
victormlg force-pushed the agent-driven-cf-reactor branch from 1468b22 to adee2f2 Compare August 21, 2026 10:56
Ticket: ENT-14398
Signed-off-by: Victor Moene <victor.moene@northern.tech>
@victormlg
victormlg force-pushed the agent-driven-cf-reactor branch from adee2f2 to a76c759 Compare August 21, 2026 11:00
Comment thread cf-reactor/cf-reactor.c
/* long options only */
case 0:
{
// TODO: handle long options if they are added in the future

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens now if a long option is passed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants